Skip to content

Move The Kody Caller To Muse Spark On Vercel AI Gateway - #104

Merged
jaywedgeworth22 merged 1 commit into
mainfrom
claude/kody-muse-spark
Oct 11, 2026
Merged

Move The Kody Caller To Muse Spark On Vercel AI Gateway#104
jaywedgeworth22 merged 1 commit into
mainfrom
claude/kody-muse-spark

Conversation

@jaywedgeworth22

@jaywedgeworth22 jaywedgeworth22 commented Oct 11, 2026

Copy link
Copy Markdown
Collaborator

Why

The owner moved Kody autofix from DeepSeek to Meta Muse Spark on 2026-10-11 (board 04b963b7, follow-up to 99e559ea).  The shared reusable now calls Vercel AI Gateway chat completions (congress-trading-shared #358 and #359).

What

  • Regenerate kody-fleet-autofix.yml with model meta/muse-spark-1.3-contributor and base URL https://ai-gateway.vercel.sh/v1.

  • The caller pins the reusable at e28fefc and forwards MODEL_API_KEY: ${{ secrets.VERCEL_AI_GATEWAY_API_KEY }} explicitly, the existing org secret.  It never uses secrets: inherit.

  • The workflow-level concurrency group stays pr-autofix-${{ github.repository }}-<PR number> with cancel-in-progress: false.  PR Autofix and Claude Code Autofix share that group, so only one autofix runs per PR at a time.

  • The kody-autofix environment remains a main-only branch gate on the generation job.  It is not a human-approval gate.

🤖 Generated with Claude Code

HARNESS @claude HARNESS
ci(kody): move the Kody caller to Muse Spark on Vercel AI Gateway
99a334a 
The owner moved Kody autofix from DeepSeek to Meta Muse Spark on 2026-10-11.  Regenerated with generate-caller.mjs against the reusable at e28fefc: model meta/muse-spark-1.3-contributor, the gateway base URL, and MODEL_API_KEY forwarded explicitly from the org secret VERCEL_AI_GATEWAY_API_KEY.  The shared pr-autofix concurrency group and 5 daily attempts are unchanged.  Boards 04b963b7 and 99e559ea.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jaywedgeworth22
jaywedgeworth22 enabled auto-merge (squash) October 11, 2026 06:53
@jaywedgeworth22
jaywedgeworth22 merged commit c27866d into main Oct 11, 2026
4 checks passed
@kody-ai

kody-ai Bot commented Oct 11, 2026 •
edited
Loading

Copy link
Copy Markdown

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

⚠️ 4 Kody Rule(s) were not evaluated

These rules declare that they need repository context beyond this diff, and the review could not retrieve it, so they were not judged on this pull request:

  • Keep server secrets out of client bundles
  • Never log tokens or credentials; only safeIssues may reach the handoff file
  • Write the shared quota-windows.json only via LocalQuotaSnapshot.write
  • Prefer Sentry for new observability; do not add new Datadog RUM/APM surfaces
Kody Guide: Usage and Configuration
Interacting with Kody

  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

​

@kody-ai

kody-ai Bot commented Oct 11, 2026

Copy link
Copy Markdown

kody code-review Business Logic medium

🤔 Insufficient Task Context

I found a task linked to this PR, but it only contains minimal information (title only, no description or acceptance criteria). To perform a meaningful business rules validation, I need more details.

🔍 What I need to validate:

  • Business requirements and acceptance criteria
  • Expected behavior and business rules
  • Edge cases and constraints to consider

💡 How to improve the task context:

  • Add a description to the linked ticket
  • Include acceptance criteria or business rules
  • Describe the expected behavior after the change

⚠️ Important:

A task title alone is not sufficient to determine whether the implementation is correct or complete.

💡 This validation runs automatically only on the first review of a pull request. To run it again, comment @kody -v business-logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jaywedgeworth22